Skip to content

Conversation

@frjo
Copy link
Member

@frjo frjo commented Jan 10, 2026

Fixes #4250

These are big updated so everything needs to be tested.

Things to test:

  • The complete login procedure.
    • With enforce 2FA
    • For staff via Google
    • Without password
    • With password
    • Forgot password
    • Change password
  • Add and remove 2FA
  • The complete submission process for new and for old users.
  • The complete review process for reviewers and for staff.
  • Alla kind of file uploads and downloads. Do they work and do they have the correct permissions.
  • Permissions for all important views.
  • Notifications via slack, e-mail etc.

@frjo frjo added Type: Maintenance Type: Major Major change, used in release drafter labels Jan 10, 2026
@frjo frjo force-pushed the maintenance/django-5-wagtail-7 branch from 24133a9 to 625e107 Compare January 10, 2026 12:32
# if child_data["type"] not in self.child_blocks:
# child_data["type"] = "char"

# return StreamValue(self, value, is_lazy=True)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs investigation.

@frjo frjo changed the title Update to Django 5.2 LTS and Wagtail 7 LTS (via Wagtail 6 LTS) Update to Django 5.2 LTS and Wagtail 7 LTS Jan 11, 2026
@frjo frjo requested a review from wes-otf January 11, 2026 14:55
@wes-otf wes-otf added the Status: Needs dev testing 🧑‍💻 Tasks that should be tested by the dev team label Jan 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Status: Needs dev testing 🧑‍💻 Tasks that should be tested by the dev team Type: Maintenance Type: Major Major change, used in release drafter

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Upgrade to Django 5.2 LTS

3 participants